![]() | ![]() | ![]() | ![]() | ![]() |
This problem occurs because the job-ordering logic separates the analyses into more than one job train; consequently, the child analysis is not forced to run after the parent.
If the date of the child analysis is in question, examine the Data Selection Details pane in the Projects workspace; the "Data as of" date for the child analysis indicates the correct date of the filtered data.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | SAS Warranty Analysis | HP-UX IPF | 4.1 | 4.31 | 9.1 TS1M3 SP4 | 9.3 TS1M0 |
64-bit Enabled Solaris | 4.1 | 4.31 | 9.1 TS1M3 SP4 | 9.3 TS1M0 | ||
64-bit Enabled AIX | 4.1 | 4.31 | 9.1 TS1M3 SP4 | 9.3 TS1M0 | ||
Microsoft Windows Server 2003 Standard Edition | 4.1 | 4.31 | 9.1 TS1M3 SP4 | 9.3 TS1M0 | ||
Microsoft Windows Server 2003 Enterprise Edition | 4.1 | 4.31 | 9.1 TS1M3 SP4 | 9.3 TS1M0 | ||
Microsoft Windows Server 2003 Datacenter Edition | 4.1 | 4.31 | 9.1 TS1M3 SP4 | 9.3 TS1M0 | ||
Microsoft Windows 2000 Server | 4.1 | 9.1 TS1M3 SP4 | ||||
Microsoft Windows 2000 Datacenter Server | 4.1 | 9.1 TS1M3 SP4 | ||||
Microsoft Windows 2000 Advanced Server | 4.1 | 9.1 TS1M3 SP4 | ||||
Microsoft Windows Server 2003 for x64 | 4.2 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
Microsoft Windows Server 2008 | 4.2 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
Microsoft Windows Server 2008 for x64 | 4.2 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 | ||
Linux for x64 | 4.2 | 4.31 | 9.2 TS2M3 | 9.3 TS1M0 |